GUI for presenting electronic messages

ABSTRACT

A method and apparatus for providing a graphical user interface to present electronic messages. In one embodiment, the method includes providing a user interface presenting a first electronic message to a recipient, where the first electronic message is associated with a segment of a second electronic message. The method further includes identifying the associated segment of the second electronic message to the recipient in the user interface, and allowing the recipient to view the second electronic message in an original form.

TECHNICAL FIELD

Embodiments of the present invention relate to data communication, andmore specifically, to providing a graphical user interface (GUI) forpresenting electronic messages.

BACKGROUND

Most business professionals today spend between 20% and 50% of theirworking time using e-mail: reading, ordering, sorting,‘re-contextualizing’ fragmented information and of course writingemails. Use of e-mail is increasing due to trends of globalization suchas distribution of organizational divisions and outsourcing.

When a user receives an email message and hits a reply button to type aresponse, an initial message is copied to a mail window buffer, and theuser can edit the initial message. For example, the user may deleteeverything but a single paragraph to which the user wants to respond.The user may then send the response to the sender of the initialmessage, as well as some other users who were not the recipients of theinitial message. Currently, the users who join the email thread latehave no way of knowing how the initial message looked like in itsoriginal form. In particular, if the initial message was partiallyerased, they cannot view the erased portions, and even if the initialmessage looks complete, they cannot be certain that it has not beenmodified by other recipients.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings and in which:

FIG. 1 illustrates a network architecture in which embodiments of thepresent invention may be implemented.

FIG. 2 is a block diagram of one embodiment of a client messagingsystem.

FIG. 3A is a flow diagram of one embodiment of a method for processing anew message at a sender messaging system.

FIG. 3B is a flow diagram of one embodiment of a method for processing anew message at a recipient messaging system.

FIG. 4 illustrates an exemplary email composition process, in accordancewith some embodiments of the invention.

FIGS. 5A, 5B, 5C and 5D illustrate exemplary user interfaces forpresenting threaded messages in a reduced format, according to someembodiments of the invention.

FIGS. 6A, 6B and 6C illustrate exemplary user interfaces for presentingthreaded messages using sticky notes, according to some embodiments ofthe invention.

FIGS. 7A and 7B illustrate exemplary user interfaces for presentingmultiple responses to a message, according to some embodiments of theinvention.

FIGS. 8A and 8B are flow diagrams of two alternative embodiments of amethod for server-based optimization of message transmission.

FIGS. 9A and 9B illustrate exemplary server-client message exchangeprocesses, in accordance with two alternative embodiments of theinvention.

FIG. 10 is a flow diagram of one embodiment of a method for uploadinguser messages to a client messaging system.

FIG. 11 is a block diagram of one embodiment of a server messagingsystem.

FIG. 12 illustrates a block diagram of an exemplary computer systemimplementing some embodiments of the present invention.

DETAILED DESCRIPTION

Described herein is a method and apparatus for providing a graphicaluser interface (GUI) to present electronic messages. Electronic messagesmay include, for example, email messages, instant messaging (IM)communications, blog entries, etc. In one embodiment, a user interfaceis provided to present a first electronic message to a recipient, wherethe first electronic message is associated with a segment of a secondelectronic message. A segment may be, for example, a message sentence, amessage paragraph, a message attachment, an image included in themessage, etc. The first electronic message may include a comment on asegment of the second electronic message. The association between thefirst electronic message and the second electronic message isgraphically illustrated in the user interface. In addition, the userinterface allows the recipient to view the second electronic message inits original, unmodified form. More details regarding the user interfacewill be discussed below.

In the following description, numerous details are set forth. It will beapparent, however, to one skilled in the art, that the present inventionmay be practiced without these specific details. In some instances,well-known structures and devices are shown in block diagram form,rather than in detail, in order to avoid obscuring the presentinvention.

Some portions of the detailed descriptions which follow are presented interms of algorithms and symbolic representations of operations on databits within a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “processing”, “updating”,“maintaining”, “determining”, “identifying” or the like, refer to theaction and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

The present invention also relates to an apparatus for performing theoperations herein. This apparatus may be specially constructed for therequired purposes, or it may comprise a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program may be stored in a computerreadable storage medium, such as, but not limited to, any type of diskincluding floppy disks, optical disks, CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring electronic instructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear as set forth in thedescription below. In addition, the present invention is not describedwith reference to any particular programming language. It will beappreciated that a variety of programming languages may be used toimplement the teachings of the invention as described herein.

A machine-accessible storage medium includes any mechanism for storingor transmitting information in a form readable by a machine (e.g., acomputer). For example, a machine-accessible storage medium includesread only memory (“ROM”); random access memory (“RAM”); magnetic diskstorage media; optical storage media; flash memory devices; electrical,optical, acoustical or other form of propagated signals (e.g., carrierwaves, infrared signals, digital signals, etc.); etc.

FIG. 1 illustrates an exemplary network architecture 100 in whichembodiments of the present invention may operate. The networkarchitecture 100 may include client devices (clients) 106, a server 102and a network 104. The clients 106 may be, for example, personalcomputers (PCs), mobile phones, palm-sized computing devices, personaldigital assistants (PDAs), and the like.

The clients 106 are coupled to the server 102 via the network 104, whichmay be a public network (e.g., Internet) or a private network (e.g.,Ethernet or a local area Network (LAN)). The server 102 providesmessaging service to the clients 106. In particular, the server 102 maybe a mail server, an instant messaging (IM) server, a blog server, etc.

Each client 106 hosts a messaging system 108 that cooperates with othermessaging systems 108 and the server 102 to facilitate exchange ofmessages between the clients 106. A messaging system 108 is responsiblefor managing messages (e.g., email messages, IM messages, blog entries,etc.) at a respective client 106. As will be discussed in more detailbelow, the messaging system 108 divides messages provided by users intosegments, stores message with identifiers of segments in a localrepository, and allows users to comment on individual segments of themessage. The messaging system 108 sends comments on specific segments tointended recipients who can then not only view the comments on theselected segments, but also the original messages from which thesegments were selected. The original messages are presented in theirinitial, unmodified form, and can include a digital signature if it wasprovided by the author of the original message.

A segment may be a message sentence, a message paragraph, a messageattachment, an image included in the message, etc. In one embodiment,the messaging system 108 is configured to specify which message portionshould constitute a segment. Such a configuration can be provided by auser or a system administrator, or be predefined.

As will be discussed in more detail below, in one embodiment, the server102 optimizes the transmission of electronic messages by keeping trackof associations between the messages (e.g., which messages were providedas comments on other messages), and transmitting to clients only thosemessages that are not stored locally at the clients.

FIG. 2 is a block diagram of one embodiment of a client messaging system200. The client messaging system 200 may include a message manager 202,a user interface module 204, and a repository 206. The message manager202 divides messages provided by a user into segments, assigns uniqueidentifiers to the segments, stores the messages with segmentidentifiers in the repository 206, and sends messages with segmentidentifiers to their intended recipients. In one embodiment, eachmessage is stored as an object (e.g., an XML object) containingidentifiers of corresponding segments and having an identifier of themessage. When a user requests to enter a new message as a comment on aspecific segment of an existing message, the message manager 202 createsan object for the new message, adds the ID of the specific segment ofthe existing message to the object of the new message, and divides thenew message into segments. Upon receiving a send request from the user,the message manager 202 stores the object of the new message locally,and sends the objects of the existing and new messages to the recipientsof the new message. In one embodiment, if the user digitally signs themessage, the digital signature is included in the object of the message.

The repository 206 stores all messages received or originated at theclient device. The messages are stored with identifiers of segment IDscontained in respective messages. In addition, when messages relate toother messages or specific segments of other messages, the associationsbetween messages and/or message segments are stored in the repository206. As discussed above, in one embodiment, the repository 206 storesmessages as objects (e.g., XML objects, SGML objects, etc.). Each objectmay have an object ID and segment IDs of segments contained in theobject. In addition, if the object relates to (e.g., includes a commenton) other segments and messages, the object may include IDs of thesesegments and messages.

In one embodiment, the message exchange process is optimized to minimizethe number of transmitted messages. As will be discussed in more detailbelow, in this embodiment, the new message may be sent to the messagemanager 202 with the dependency chain information compiled by a server(e.g., server 102). The dependency chain information specifies messagesto which the current message relates (e.g., using object IDs of thesemessages). Upon receiving a new message with dependency chaininformation, the message manager 202 determines which of the messagesspecified in the dependency chain are not stored in the repository 206,and sends a request for those messages to the server. Upon receiving therequested messages from the server, the message manager 202 stores themin the repository 206.

The user interface module 204 provides graphical user interfaces (GUIs)to present messages to the user. A GUI allows a user to selectindividual segments in the message and provide comments on theindividual segments. In one embodiment, the GUI displays the selectedsegment without displaying the entire message, and graphicallyillustrates that the comment relates to the selected segment (e.g., byhighlighting the selected segment, placing brackets around the selectedsegment, etc.). The GUI may also provide a control (e.g., a button)allowing a user to view the entire message in its original (unmodified)form. In another embodiment, the GUI displays the comment as a note(e.g., a sticky note) added to the message and positioned next to, or ontop of, the selected segment in the message, where the content of themessage is displayed in its original form. The GUI may also provide acontrol allowing a user to view all messages or comments related to aspecific segment of the message, and may display all the relatedmessages or comments as notes positioned next to, or on top of, thespecific segment.

In one embodiment, in which the original message has been signed by itsauthor, the GUI notifies the viewer that the original message has adigital signature. If the GUI presents to a user a thread of messagesand some of the messages have been digitally signed, the user can seewhich messages have digital signatures.

Accordingly, embodiments of the invention allow users to comment oninitial messages without modifying the initial messages. The commentsare maintained separately from the initial messages, preserving theoriginality and separateness of related messages.

FIG. 3A is a flow diagram of one embodiment of a method 300 forprocessing a message at a sender's client device. The method 300 may beperformed by processing logic that may comprise hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (such as instructions run on a processing device), or acombination thereof. In one embodiment, the method 300 is performed by aclient messaging system 108 of FIG. 1.

Referring to FIG. 3A, method 300 begins with processing logic creatingobject for message 1 and assigning a message ID to message 1 (block302). Object 1 may be created when the user sends a request to provide anew message (e.g., by activating a new message button). Alternatively,object 1 may be created when the user enters message 1 and submits arequest to send message 1 to one or more recipient. Object 1 may be, forexample, an XML object, an SGML object, etc.

At block 304, processing logic divides message 1 into segments, assignsa segment ID to each segment, and adds segment IDs to the object ofmessage 1. As discussed above, depending on the configuration, a segmentmay be a message sentence, a message paragraph, a message attachment, animage within the message, etc. Processing logic may divide message 1into segments while the user is entering message 1. For example, if aparagraph constitutes a segment, processing logic adds a new segmenteach time the user hits the enter key to start a new paragraph.Alternatively, processing logic may divide message 1 into segments whenthe user completes entering message 1 (e.g., when the user hits the sendbutton).

At block 308, processing logic stores object 1 in a local repository. Atblock 310, processing logic sends object 1 to the intended recipient(s)of message 1.

FIG. 3B is a flow diagram of one embodiment of a method 320 forprocessing a message at a recipient's client device. The method 320 maybe performed by processing logic that may comprise hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (such as instructions run on a processing device), or acombination thereof. In one embodiment, the method 320 is performed by aclient messaging system 108 of FIG. 1.

Referring to FIG. 3B, method 320 begins with processing logic receivingand storing object 1 in a local repository of a recipient's clientdevice (block 322). At block 324, processing logic displays message 1 tothe recipient.

At block 326, processing logic receives user selection of segment A inmessage 1. The user may select segment A by activating an indicator(e.g., an icon, paragraph number, etc.) associated with segment A,clicking on segment A, etc. In response, processing logic visuallyindicates the user selection of segment A on the screen. For example,processing logic may delete everything but the selected segment fromdisplayed message 1 and put brackets around the selected segment, or itmay highlight the selected segment, or display it in a different coloror with a higher intensity than the rest of the message, etc.

At block 328, processing logic receives a user request to enter acomment for (or a response to) segment A and creates object 2 for thecomment. The user request may be received when the user activates adesignated button on the screen.

In an alternative embodiment, processing logic first receives the userrequest to enter a comment, and then allows a user to select a segmentfor which the comment is to be entered. An exemplary user interfaceillustrating the above capability with be discussed in more detail belowin conjunction with FIG. 5D.

At block 330, processing logic allows the user to enter the commentwhile preventing the user from modifying the content of segment A. Whilethe user is entering the comment, processing logic identifies segmentsin the comment, and adds their segment IDs to object 2. In oneembodiment, processing logic allows the user to enter the comment in adesignated area (e.g., above or below segment A). In another embodiment,processing logic displays a note (e.g., a sticky note) close to, or ontop of, segment A and allows the user to enter the comment in the note.In yet another embodiment, processing logic allows the user to enter thecomment in a designated area (e.g., above or below segment A), and thenadds a note close to, or on top of, segment A and displays the commentin this note.

Upon receiving a user request to send message 2 (the comment on segmentA) to one or more recipients, processing logic stores object 2 in thelocal repository (block 334). Similar to message 1, message 2 includesits message ID, segment IDs of the segments within message 2, and thesegment ID of segment A. Further, at block 336, processing logic sendsobject 1 and object 2 to the recipients of message 2.

FIG. 4 illustrates an exemplary email composition process, in accordancewith some embodiments of the invention. In particular, client 1 createsobject 1 for email 1. Email 1 includes segments A, B and C specified inobject 1 using corresponding segment identifiers. Client 1 stores object1 in a local repository and sends object 1 to its recipient (user ofclient 2).

Client 2 receives object 1, stores object 1 in a local repository, anddisplays email 1 to the user. When client 2 receives the user'sselection of segment B in email 1 and detects the user's activation ofthe reply or forward button, client 2 graphically illustrates thatsegment B has been selected and allows the user to comment on segment B.In one embodiment, client 2 deletes everything from message 1, exceptsegment B, and displays segment B surrounded by brackets. In anotherembodiment, client 2 adds a note (e.g., a sticky note) close to, or ontop of segment B, for entering the comment.

Upon detecting the user's activation of the reply or forward button,client 2 creates object 2 with segment ID of segment B. As the userenters email 2, client 2 divides email 2 into segments D, E and F, andadds IDs of these segments to object 2. When the user activates the sendbutton, client 2 stores object 2 in the local repository and sendsobjects 1 and 2 to a recipient of email 2 (client 3).

Client 3 receives objects 1 and 2, stores them in a local repository,and displays email 2 to a user. In particular, in one embodiment, client3 parses object 2 to determine ID of segment B, extracts segment B fromobject 1, and displays email 2 as a comment on segment B. In oneembodiment, client 3 displays email 2 above or below segment B, withoutdisplaying in the entire email 1. In another embodiment, client 3displays email 3 in a sticky note attached to segment B of displayedemail 1. In yet another embodiment, client 3 displays email 1 in itsoriginal form, and when the user places the cursor over segment B,client 3 displays email 1 next to, or on top of, segment B (e.g., in abox, sticky note, etc.), with email 1 being visible as long as thecursor remains in the area covering segment B. Once the user moves thecursor outside of this area, email 1 disappears from the screen.

If the user of client 3 desires to see email 1 in its original form, theuser can activate a designated control presented on the screen. Inresponse, client 3 retrieves object 1 and displays email 1 in itsoriginal form to the user.

FIGS. 5A, 5B and 5C illustrate exemplary user interfaces (UI) forpresenting threaded messages in a reduced format, according to someembodiments of the invention. Referring to FIG. 5A, UI 500 displays anemail message 500 presented to a user (e.g., a recipient). If the userwants to comment on a specific segment (e.g., segment 502), the user canselect this segment. For example, the user can select segment 502 with acursor, click (e.g., double click, left-click, right-click) on anyportion of segment 502 or an indicator (not shown) associated withsegment 503, etc. Once the user selects segment 502 and activates Replyor Forward button (not shown), the message 500 disappears from thescreen, leaving only segment 502 surrounded by brackets, and an area isprovided on top of segment 502 to enter a comment. The user can thenenter a comment and activate Send button to transmit the comment to itsintended recipient.

As discussed above, in one embodiment, the client messaging systemcreates an object for email message 500 and an object for a new emailmessage including the comment, and sends both objects to the recipient.Both objects include their object IDs and IDs of segments included inrelevant objects. In addition, the object of the new email messageincludes the ID of related segment 502.

FIG. 5B illustrates UI 510 displaying the comment to the recipient. Inparticular, UI 510 presents selected segment 514 and comment 512. UI 510also includes a button 516 to view the original message. Once the useractivates button 516, the original message is presented in its initial,unmodified form. In one embodiment, the client messaging system ensuresthat the original message is presented in unmodified form by storing theoriginal email as an unmodifiable object and transmitting this object toeach participant of the relevant email thread. UI 510 is composed byparsing an object created for comment 512, finding the ID of segment514, and extracting segment 514 from the object of the original email.

FIG. 5C illustrates UI 520 displaying a comment on another segment to arecipient. In particular, a viewer of UI 510 of FIG. 5B can selectsegment 524 from comment 512, add a new comment 522, and send theresulting message to the recipient. UI 520 shown in FIG. 5C presents thenew message to the recipient and allows the recipient to view the entirecomment 512 via the button 526.

UI 520 also includes a button 528 to view a complete thread. Inparticular, the activation of button 528 causes all messages in thethread to be displayed in their entirety, with graphical indication ofassociations between messages. For example, the original message 500 maybe displayed at the bottom of the screen in black, with segment 514being displayed in red. Comment 512 may be displayed above message 500,and may also be displayed in red to show association with segment 514.Similarly, segment 524 in comment 512 may be displayed in green, as wellas the associated comment 522, which may be displayed above comment 512.

In one embodiment, recreation of original content of messages in thethread is performed using data contained in the objects of messagescomprising the tread. As a result, users coming into the thread at anypoint of time can see original content of all messages in the thread. Inone embodiment, if any message in the thread was digitally signed,digital signature information is also presented to the users.

Referring to FIG. 5D, UI 530 illustrates an embodiment, in which theuser first hits the reply button and then selects a segment on which tocomment. In particular, the user can select segment 532 (e.g., byhitting the enter key when placing the cursor at the end of segment 532,clicking or double-clicking on segment 532, etc.), and provide comment534 for segment 532. The user can further select segment 536 and providecomment 538 for segment 536. In one embodiment, both comments 534 and538 are included in the same object in association with IDs of segments532 and 536 respectively. Alternatively, each of the two comments isincluded in a separate object in association with a correspondingsegment ID.

When the user activates Send button, the object(s) with the comments is(are) transmitted to its intended recipient. When viewing the comments,the recipient may request to view the initial message in its original,unmodified form by activating a designated button presented on thescreen (similar to button 516 in FIG. 5B).

FIGS. 6A, 6B and 6C illustrate exemplary user interfaces for viewingthreaded messages using sticky notes, according to some embodiments ofthe invention. Referring to FIG. 6A, UI 600 presents the initial messageincluding segment 602. Sticky note 604 is attached to segment 602 andincludes a comment added to segment 602. In one embodiment, note 604 isdisplayed in UI 600 temporarily, i.e., only when the cursor is placed inthe area covering segment 602. Once the user moves the cursor away fromthe area, note 604 disappears from the screen. In another embodiment,note 604 is a permanent part of the message displayed in UI 600.

Referring to FIG. 6B, UI 610 presents nested sticky notes. Inparticular, UI 610 displays the initial message including segment 602with sticky note 604 added to segment 602. A further comment made to asegment in comment 604 is presented as another sticky note 614 attachedto this segment of comment 604. Alternatively, sticky note 604 may onlyappear while the cursor is placed in the area covering the segment 602,and sticky note 614 may only appear when the cursor is moved to the areaof sticky note 604.

Referring to FIG. 6C, UI 620 presents sticky notes added to differentsegments of the message. In particular, UI 620 displays the initialmessage including segment 602 with sticky note 626 attached to segment602, and segment 622 with sticky note 624 attached to segment 622.Hence, the user can see the original content of the initial message aswell as subsequent comments made on segments of the initial message bydifferent users.

FIGS. 7A and 7B illustrate exemplary user interfaces for viewingmultiple responses to a message, according to some embodiments of theinvention. Referring to FIG. 7A, UI 700 presents an original message toa user, and includes a button 704 allowing the user to view allresponses or comments provided for the original message. FIG. 7B showsall comments provided by different users on segment 702 of the originalmessage. The comments are presented in the form of sticky notes 712,714, 716 and 718 positioned in the area of segment 702.

In an alternative embodiment, instead of activating button 704, the usercan place the cursor in the area covering the selected segment, and theUI will present all comments pertaining to this segment. The commentswill be displayed as long as the cursor is placed in this area. Once theuser moves the cursor to the area covering another segment, thepreviously-displayed comments disappear, and the comments pertaining tothe newly selected segment become visible.

In some embodiments, message exchange between clients is optimized byutilizing a server that minimizes amount of data transmitted betweenclients. In one embodiment, the server maintains information on whatclients store which messages. In another embodiment, the server does notmaintain such information but rather waits for clients to requestmessages not stored locally at the relevant clients.

FIGS. 8A and 8B are flow diagrams of two alternative embodiments of amethod for server-based optimization of message transmission. The methodmay be performed by processing logic that may comprise hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (such as instructions run on a processing device), or acombination thereof. In one embodiment, the method is performed by aserver 102 of FIG. 1.

Referring to FIG. 8A, method 800 begins with processing logicmaintaining a database that stores messages exchanged between differentclients (block 802). For each message, processing logic records in thedatabase information on clients that store the message locally.Processing logic may record this information upon receiving a messagefrom a client or transmitting the message to a client. In oneembodiment, messages are stored in the database as objects (e.g., XMLobjects). Each object may include an object ID, IDs of segmentscontained in a respective message, and IDs of other messages andsegments to which the respective message relates if any (e.g., if themessage was provided as a comment on another message or a segment ofanother message).

At block 804, processing logic receives a message from a client anddetermines that this is a new message that is not stored in thedatabase. The new message may specify a sender and recipient, and may ormay not be associated with an existing message (e.g., be a comment on asegment of an existing message). In one embodiment, the client onlytransmits new messages (messages that are created at the client), andprocessing logic does not need to determine whether a message receivedfrom the client is new. In another embodiment, messages transmitted bythe client are not limited to those created at the client; henceprocessing logic has to determine whether a message received from theclient is already stored in the database.

At block 806, processing logic determines whether the new message isassociated with any messages stored in the database. In one embodiment,this determination is made based on an associated message ID orassociated segment ID contained in the object of the new message. Forexample, if the new messages is a comment on a segment of an existingmessage, the object of the new message will include an ID of thissegment.

If the new message is not associated with any messages stored in thedatabase, processing logic sends the new message to its intendedrecipient(s) (block 812), and proceeds to block 818.

If the new message is associated with one or more messages stored in thedatabase, processing logic determines whether the associated messagesare stored locally at the recipient(s) (block 808). If all associatedmessages are stored locally at the recipient(s), processing logic sendsonly the new message to the recipient(s) (block 810) and proceeds toblock 818. As discussed above, the new message may be sent in the formof an object that includes an ID of a message or message segment towhich the new message relates.

If not all associated messages are stored locally at the recipient(s),processing logic sends to the recipient(s) the new message and eachassociated message that is not stored locally at the recipient(s) (block814) and proceeds to block 818.

At block 818, processing logic stores the new message in the database,along with the information on the message sender and recipient(s) thatindicates which clients store this message locally (block 818).

Referring to FIG. 8B, method 830 does not record information on whatclients store which messages but instead waits for client to requestmessages that are not stored locally at the clients. In particular, uponreceiving a new message from a client (block 832), processing logicdetermines whether the new message is associated with any messagesstored in the centralized database. In one embodiment, thisdetermination is made based on an associated message ID or associatedsegment ID contained in the object of the new message. For example, ifthe new messages is a comment on a segment of an existing message, theobject of the new message will include an ID of this segment.

If the new message is not associated with any messages stored in thedatabase, processing logic sends the new message to its intendedrecipient(s) (block 836), and proceeds to block 818.

If the new message is associated with one or more messages stored in thedatabase, processing logic determines a dependency chain for the newmessage (block 808). The dependency chain can be determined by findingmessages on which the new message depends. Each of the found messages isfurther examined for dependencies, etc. The dependency chain processends when no more dependencies of previously found messages exist.

At block 840, processing logic sends the new messages with thedependency chain information to the recipient. At block 842, processinglogic stores the new message in the centralized database.

When the recipient's client receives the new message with the dependencychain, it determines which messages specified in the dependency chainare not stored locally, and requests such messages from the server. Uponreceiving the messages from the server, the recipient's client candisplay the original message thread or any individual messages from thethread if requested by the user.

FIG. 9A illustrates an exemplary server-client message exchange process,in accordance with an embodiment discussed above in conjunction withFIG. 8A. Referring to FIG. 9A, client 900 creates object 1 for message1, sends object 1 to a message recipient (client 904) via server 902,and stores object 1 in a local repository.

Server 902 receives object 1, stores object 1 in the centralizeddatabase, and sends object 1 to client 904. Server 902 also records thatobject 1 is stored locally at client 900 and client 904.

Client 904 stores object 1 locally and displays message 1 to a user. Ifthe user decides to provide a comment on a segment (e.g., segment A) ofmessage 1, client 904 creates object 2 for the comment and includes IDof segment A in object 2. Client 904 then sends object 2 back to client900 via server 902, and stores object 2 locally.

Server 902 determines that object 2 is a new object that relates toobject 1, and stores object 2 in the centralized database. Server 902also determines that client 900 stores object 1 locally, and sends onlyobject 2 to client 900. Server 902 also records that object 2 is storedlocally at client 900 and client 904.

Client 900 stores object 2 in a local repository and determines thatobject 2 relates to segment A from object 1. Client 900 retrieves object1 from the local repository and composes message 2 for viewing. In oneembodiment, message 2 includes the comment from object 2, and segment Aextracted from object 1. In another embodiment, message 2 includesmessage 1 with a sticky note attached to segment A, where the stickynote includes the comment from object 2. If the user of client 900 wantsto see message 1 in its original form, client 900 retrieves message 1from its local repository and displays message 1 to the user.

FIG. 9B illustrates an exemplary server-client message exchange process,in accordance with another embodiment discussed above in conjunctionwith FIG. 8B. Referring to FIG. 9B, client 920 creates object 1 formessage 1, sends object 1 to a message recipient (client 924) via server922, and stores object 1 in a local repository.

Server 922 receives object 1 and parses object 1 to determine whether itrelates to another message. Upon determining that message 1 does notdepend on any other messages, server 922 stores object 1 in thecentralized database, and sends object 1 to client 904.

Client 924 stores object 1 locally and displays message 1 to a user. Ifthe user decides to provide a comment on a segment (e.g., segment A) ofmessage 1, client 924 creates object 2 for the comment and includes IDof segment A in object 2. Client 924 then sends object 2 to client 920via server 922, and stores object 2 locally.

Server 922 determines that object 2 relates to object 1, and determine adependency chain for object 2. In particular, server 922 adds the ID ofobject 1 to the dependency chain, retrieves object 1 from the database,and parses object 1 to determine whether message 1 depends on any othermessages. Upon determining that object 1 does not depend on any othermessages, server 922 sends object 2 and its dependency chain informationto client 920. Server 922 also stores object 2 in the centralizeddatabase.

Client 920 stores object 2 in a local repository, and examines thedependency chain information to determine whether it needs to send arequest to server 922 for any objects not stored locally at client 920.Upon determining that object 1 is stored locally, client 920 retrievesobject 1 from the local repository and composes message 2 for viewing.

In some circumstances, messages pertaining to a user may need to beuploaded from a server to a client messaging system. For example, allmessages pertaining to a user may be stored at a server and uploaded toa client messaging system only upon a user request. In another example,messages pertaining to a user may need to be uploaded to a clientmessaging system when a new client messaging system is installed.

FIG. 10 is a flow diagram of one embodiment of a method 1000 foruploading user messages to a client messaging system. The method 1000may be performed by processing logic that may comprise hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (such as instructions run on a processing device), or acombination thereof. In one embodiment, the method 1000 is performed bya server 102 of FIG. 1.

Referring to FIG. 10, method 1000 begins with processing logic receivinga client request to upload user messages from a server (block 802). Inone embodiment, processing logic authenticates the client to verify thatthe client is authorized to request user messages.

At block 1004, processing logic searches a centralized database formessages having the user as a sender or a recipient. At block 1006,processing logic adds such messages to a list of user messages.

At block 1008, processing logic examines each message on the list todetermine whether this message relates to any other message that is noton the list. If so, processing logic retrieves the related message fromthe centralized database (block 1010), adds it to the list (block 1012),and returns to block 1008. When all related messages are added to thelist, processing logic sends all messages on the list to the client(block 1014).

FIG. 11 is a block diagram of one embodiment of a server messagingsystem 1100. The server messaging system 1100 may include an objectmanager 1102 and a database 1104. The database 1101 stores messagesexchanged between different clients, as well as information identifyingclients that store individual messages locally. In one embodiment,messages are stored in the database 1104 as objects (e.g., XML objects).Each object may include an object ID, IDs of segments contained in arespective message, and IDs of other messages and segments to which therespective message relates if any (e.g., if the message was provided asa comment on another message or a segment of another message).

In one embodiment, the object manager 1102 receives messages fromdifferent clients and determines what should be sent to intended messagerecipients. In particular, the object manager 1192 looks for relatedmessages and sends to the recipients only those related messages thatare not currently stored at the respective recipients, thus minimizingthe number of transmitted messages.

In another embodiment, the object manager 1102 receives messages fromdifferent clients, and determines a dependency chain for each receivedmessage. The dependency chain indicates which messages are related tothe received message. The object manager 1102 sends the received messagewith its dependency chain information to the recipient, and waits forthe recipient to request messages specified in the dependency chain thatare not stored locally at the recipient. Upon receiving a request forsuch messages, the object manager 1102 retrieves these messages from thedatabase 1104 and sends them back to the recipient.

In one embodiment, the object manager 1102 is also responsible foruploading messages pertaining to a user to a client messaging system.Prior to uploading, the object manager 1102 searches the database 1104to compile a list of messages for which the user is either a sender or arecipient, and then examines each message on the list to determinewhether it has related messages. If it does, the object manager 1102further examines each related message to determine whether it depends onany other messages. This process continues until none of the examinedmessages have related messages.

FIG. 12 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system 1200 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeembodiments, the machine may be connected (e.g., networked) to othermachines in a Local Area Network (LAN), an intranet, an extranet, or theInternet. The machine may operate in the capacity of a server or aclient machine in client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a server, a network router, switch or bridge, or any machinecapable of executing a set of instructions (sequential or otherwise)that specify actions to be taken by that machine. Further, while only asingle machine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein.

The exemplary computer system 1200 includes a processing device 1202, amain memory 1204 (e.g., read-only memory (ROM), flash memory, dynamicrandom access memory (DRAM) such as synchronous DRAM (SDRAM) or RambusDRAM (RDRAM), etc.), a static memory 1206 (e.g., flash memory, staticrandom access memory (SRAM), etc.), and a data storage device 1218,which communicate with each other via a bus 1230.

Processing device 1202 represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, the processing device may be complex instruction setcomputing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,or processor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processing device 1202may also be one or more special-purpose processing devices such as anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), network processor,or the like. The processing device 1202 is configured to execute theprocessing logic 1226 for performing the operations and steps discussedherein.

The computer system 1200 may further include a network interface device1208. The computer system 1200 also may include a video display unit1210 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)),an alphanumeric input device 1212 (e.g., a keyboard), a cursor controldevice 1214 (e.g., a mouse), and a signal generation device 1216 (e.g.,a speaker).

The data storage device 1218 may include a machine-accessible storagemedium 1230 on which is stored one or more sets of instructions (e.g.,software 1222) embodying any one or more of the methodologies orfunctions described herein. The software 1222 may also reside,completely or at least partially, within the main memory 1204 and/orwithin the processing device 1202 during execution thereof by thecomputer system 1200, the main memory 1204 and the processing device1202 also constituting machine-accessible storage media. The software1222 may further be transmitted or received over a network 1220 via thenetwork interface device 1208.

While the machine-accessible storage medium 1230 is shown in anexemplary embodiment to be a single medium, the term “machine-accessiblestorage medium” should be taken to include a single medium or multiplemedia (e.g., a centralized or distributed database, and/or associatedcaches and servers) that store the one or more sets of instructions. Theterm “machine-accessible storage medium” shall also be taken to includeany medium that is capable of storing, encoding or carrying a set ofinstructions for execution by the machine and that cause the machine toperform any one or more of the methodologies of the present invention.The term “machine-accessible storage medium” shall accordingly be takento include, but not be limited to, solid-state memories, optical andmagnetic media, and carrier wave signals.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other embodiments will beapparent to those of skill in the art upon reading and understanding theabove description. The scope of the invention should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

What is claimed is:
 1. A computer-implemented method comprising:identifying a first electronic message and a selected segment of aplurality of segments of a second electronic message, where the firstelectronic message was created in response to the selected segment ofthe second electronic message and has a plurality of recipients;providing a user interface presenting the first electronic message andthe selected segment of the second electronic message to each recipientof the plurality of recipients without presenting other segments of thesecond electronic message to the plurality of recipients, where the userinterface presents the selected segment of the second electronic messagetogether with an original message user interface (UI) element and amessage thread UI element, the original message UI element providing anoption to view the second electronic message in an original form, andthe message thread UI element providing an option to view a messagethread comprising the first electronic message and the second electronicmessage; upon detecting a selection of the original message UI elementin the user interface by a recipient of the plurality of recipients,presenting to the recipient the second electronic message in theoriginal form; and upon detecting a selection of the message thread UIelement by a recipient of the plurality of recipients, presenting to therecipient the message thread comprising the first electronic message andthe second electronic message.
 2. The method of claim 1 wherein each ofthe first electronic message and the second electronic message is anyone of an email message, an instant message, or a blog entry.
 3. Themethod of claim 1 wherein each segment is any one of a message sentence,a message paragraph, a message attachment, or an image included in thefirst electronic message.
 4. The method of claim 1 wherein the firstelectronic message is sent to each recipient by a sender to comment onthe segment of the second electronic message.
 5. The method of claim 1wherein providing the user interface comprises: graphically illustratingthat the first electronic message is associated with the selectedsegment of the second electronic message.
 6. The method of claim 5wherein the original message UI element is a control allowing therecipient to request the second electronic message in the original form.7. The method of claim 1 wherein: the first electronic message isdisplayed as a note attached to the user-selected segment of the secondelectronic message; and presenting to the recipient the secondelectronic message in the original form comprises displaying the secondelectronic message in the original form with the note attached to theuser-selected segment of the second electronic message, the attachednote including the first electronic message.
 8. The method of claim 1further comprising: ensuring that the second electronic messagedisplayed in the original form has not been modified after being createdby a sender of the second electronic message.
 9. The method of claim 8wherein ensuring that the second electronic message displayed in theoriginal form has not been modified comprises: retrieving an objectcreated for the second electronic message, the object of the secondelectronic message being unmodifiable; and displaying the secondelectronic message in the original form using the retrieved object. 10.The method of claim 1 wherein providing the user interface presentingthe first electronic message to each recipient comprises: receiving anobject created for the first electronic message and an object createdfor the second electronic message; determining, based on the object ofthe first electronic message, that the first electronic message includesa comment on the user-selected segment of the second electronic message;and extracting the user-selected segment of the second electronicmessage from the object of the second electronic message using a segmentidentifier contained in the object of the first electronic message. 11.The method of claim 1 wherein: the second electronic message isdigitally signed; and allowing the recipient to view the secondelectronic message in the original form comprises displaying the secondelectronic message with a digital signature.
 12. The method of claim 1wherein: the first electronic message is digitally signed; and the userinterface displays the first electronic message with a digitalsignature.
 13. The method of claim 1 further comprising: providing inthe user interface a control to request all electronic messagespertaining to the user-selected segment of the second electronicmessage; and displaying all electronic messages pertaining to theuser-selected segment of the second electronic message.
 14. A systemcomprising: a memory; a processing device, coupled to the memory; amessage manager to cause the processing device to receive a firstelectronic message associated with a second electronic message having aplurality of segments and created prior to the first electronic message,wherein the first electronic message was created in response to auser-selected segment of the plurality of segments of the secondelectronic message; and a user interface module, coupled to the messagemanager, to provide a user interface presenting the first electronicmessage and the user-selected segment of the second electronic messageto each recipient of a plurality of recipients without presenting othersegments to the plurality of recipients of the second electronicmessage, where the user interface presents the user-selected segment ofthe second electronic message together with an original message userinterface (UI) element facilitating a request of a recipient of theplurality of recipients to view the second electronic message in anoriginal form, and a message thread UI element facilitating a request ofthe recipient to view a message thread comprising the first electronicmessage and the second electronic message, where the user interfacemodule is to detect a selection of the original message UI element inthe user interface, the selection of the original UI element indicatingthe request of the recipient to view the second electronic message inthe original form, and to display to the recipient the second electronicmessage in the original form in response to the selection of theoriginal message UI element in the user interface, and where the userinterface module is to detect a selection of the message thread UIelement in the user interface, the selection of the message thread UIelement indicating the request of the recipient to view the messagethread comprising the first electronic message and the second electronicmessage, and to display to the recipient the message thread in responseto the selection of the message thread UI element in the user interface.15. The system of claim 14 wherein the user interface graphicallyillustrates that the first electronic message is associated with theuser-selected segment of the second electronic message, the userinterface further including a control allowing the recipient to requestthe second electronic message be presented in the original form.
 16. Thesystem of claim 14 wherein the user interface displays the firstelectronic message as a note attached to the user-selected segment ofthe second electronic message, the content of the first electronicmessage being displayed in the original form.
 17. The system of claim 14wherein the user interface module is to display the second electronicmessage in the original form using an object created for the secondelectronic message, the object of the second electronic message beingunmodifiable.
 18. The system of claim 14 wherein the message manager isfurther to receive an object created for the first electronic messageand an object created for the second electronic message, to determine,based on the object of the first electronic message, that the firstelectronic message includes a comment on the segment of the secondelectronic message, and to extract the segment of the second electronicmessage from the object of the second electronic message using a segmentidentifier contained in the object of the first electronic message. 19.The system of claim 14 wherein the user interface includes a control torequest all electronic messages pertaining to the segment of the secondelectronic message.
 20. A non-transitory computer-readable storagemedium including instructions that, when accessed by a processingdevice, cause the processing device to perform a method comprising:identifying a first electronic message and a selected segment of aplurality of segments of a second electronic message, where the firstelectronic message was created in response to the selected segment ofthe second electronic message; providing a user interface presenting thefirst electronic message and the selected segment of the secondelectronic message to each recipient of a plurality of recipientswithout presenting other segments of the second electronic message tothe plurality of recipients, where the user interface presents theselected segment of the second electronic message together with anoriginal message user interface (UI) element and a message thread UIelement, the original message UI element providing an option to view thesecond electronic message in an original form, and the message thread UIelement providing an option to view a message thread comprising thefirst electronic message and the second electronic message; upondetecting a selection of the original message UI element in the userinterface by a recipient of the plurality of recipients, presenting tothe recipient the second electronic message in the original form; andupon detecting a selection of the message thread UI element by arecipient of the plurality of recipients, presenting to the recipientthe message thread comprising the first electronic message and thesecond electronic message.
 21. The non-transitory computer-readablestorage medium of claim 20 wherein: each of the first electronic messageand the second electronic message is any one of an email message, aninstant message, or a blog entry; and each segment is any one of amessage sentence, a message paragraph, a message attachment, or an imageincluded in the first electronic message.
 22. The non-transitorycomputer-readable storage medium of claim 20 wherein: the originalmessage UI element comprises a control allowing the recipient to requestthe second electronic message be displayed in the original form.
 23. Thenon-transitory computer-readable storage medium of claim 20 wherein: thefirst electronic message is displayed as a note attached to theuser-selected segment of the second electronic message.
 24. Thenon-transitory computer-readable storage medium of claim 20 whereinproviding the user interface presenting the first electronic message tothe recipient comprises: receiving an object created for the firstelectronic message and an object created for the second electronicmessage; determining, based on the object of the first electronicmessage, that the first electronic message includes a comment on thesegment of the second electronic message; and extracting the segment ofthe second electronic message from the object of the second electronicmessage using a segment identifier contained in the object of the firstelectronic message.